OSynC for Max / Live 0.7a, 3 July 2012

OSynC is a way to synchronise performers or computers with OSC.  It is designed to be a stateless system, where performers can join or leave a performance, and receive tempo/time signature and other positional information on a number of time scales to remain in sync effortlessly.  It can also be used as a ReWire-like way to synchronise note-generating events across applications. 

Order of messages within an OSynC datagram:

	/osync/timestamp 773495082.
	/osync/play 1
	/osync/bpm 125.7
	/osync/timesig 4 4
	/osync/fractime 59.665871
	/osync/barcount 12
	/osync/bar 4
	/osync/beat 3
	/osync/fraction 18
	/osync/ramp 0.578125


Usage:
Place the OSynC class files in [Max app folder]/Cycling '74/java/classes and the help files in [Max app folder]/Cycling '74/java/help

The OSynC4Transport and OSynC4Live objects have been written in Java.  They can be instantiated with [mxj OSynC4Transport] and [mxj OSynC4Live].

[mxj OSynC4Transport] is designed to grab transport information from Max's [transport] and format those messages as OSC packets.

[mxj OSynC4Live] is designed to send information from a MaxForLive and gets transport information differently (with [plugsync~]) hence the different versions.


Please see the enclosed OSynC4Transport-Help.maxpat help patch for usage.  These are still alpha so please test these thoroughly before using in a live context.



Java source files included.  I'm not a programmer.  Suggestions welcome.
Questions/comments? alex@x37v.com

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. http://creativecommons.org/licenses/by-nc-sa/3.0/